home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 41 lines | [TEXT/GEOL] |
- Item 0714859 2-Aug-89 18:54
-
- From: MCCARTHY4 McCarthy, Brendan
-
- To: D2086 Efficient Field Svc, C Faith, PRT
-
- cc: MACAPP.TECH$ MACAPP Tech
-
- Sub: Response to Really nasty…
-
- Hi Curt,
-
- I also encountered this phenomenon when converting from ß5 to ß9. It's not a
- bug in MacApp, but something more insidious (read "I spent a couple of very
- frustrating hours in TMON trying to debug this one.")
-
- In general, your problem is that you must have some object file that was
- created with compiler options that differ from those that MacApp 2.0ß9 uses.
- The particular option that hosed me was the '-mbg ch8' option. Apparently, MPW
- v2.0 compatible MacsBug symbols are MacApp v2.0ß9 incompatible.
-
- From the listing you posted, I would suspect UDynArray.p.o.
-
- Now for the (partial) flame:
- <<flame on>>
- I encountered this problem (and several other time-burners) while trying to
- create a library that includes object files from a couple of my own MacApp
- units, plain Pascal, assembly, and C. I wish the MAmake mechanism was a little
- more flexible.
- Currently, it assumes that you want an application whenever you build anything
- with MacApp. In my case, in order to correctly create the library, I had to
- hack the 'Build Rules and Dependencies' script to echo {PascalOptions} so I
- could see what they were (since they are UnExported when the MAmake tool is
- finished executing.) Then I had to use those same Pascal options to create a
- bogus SomethingLib.MAmake file script.
- << flame off>>
-
- Hope that helps,
- Brendan McCarthy
-
-